Skip to content

Conversation

@o-liver
Copy link
Member

@o-liver o-liver commented Oct 10, 2024

Remove old node 16 images and add new node 22, which is also the latest now.

Remove old node 16 images and add new node 22, which is also the latest now.
@o-liver o-liver self-assigned this Oct 10, 2024
@o-liver
Copy link
Member Author

o-liver commented Oct 10, 2024

FYI
https://nodejs.org/en/about/previous-releases
There is always an Active LTS and Maintenance LTS. Current Active LTS is node 20, but October 22 Active LTS will be node 22, and node 20 will be Maintenance LTS.
April 2025 node 18 goes out of maintenance.

docker push ppiper/node-browsers:${{ matrix.base-image-tag }}
docker push ghcr.io/sap/ppiper-node-browsers:${{ matrix.base-image-tag }}
if [ "${{ matrix.base-image-tag }}" == 20-bookworm ]; then
if [ "${{ matrix.base-image-tag }}" == 22-bookworm ]; then
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kaylinche Question: should we already tag node 22 as latest, or wait for the official switch as Active LTS before tagging it latest?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my side it is fine to tag 22 already as latest.

@o-liver o-liver merged commit 3d1714d into master Oct 11, 2024
@o-liver o-liver deleted the node22 branch October 11, 2024 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants